[DOCS] Adds more authorization info for CCR APIs#35606
Conversation
lcawl
added
>docs
|
Pinging @elastic/es-distributed |
|
Pinging @elastic/es-security |
lcawl
force-pushed
the
lcawley-ccr-auth2
branch
from
5f57261 to
f273830
Compare
|
|
||
| ==== Authorization | ||
|
|
||
| If the {es} {security-features} are enabled, you must have `read` and `monitor` |
There was a problem hiding this comment.
Cluster monitor privileges are needed to use this api in the follower cluster.
There was a problem hiding this comment.
I'm assuming this is instead of read and monitor index privileges. If that's not correct, please let me know.
|
|
||
| ==== Authorization | ||
|
|
||
| If the {es} {security-features} are enabled, you must have `manage_follow_index` |
There was a problem hiding this comment.
only manage_follow_index is needed in the follower cluster.
|
|
||
| ==== Authorization | ||
|
|
||
| If the {es} {security-features} are enabled, you must have `read` and `monitor` |
There was a problem hiding this comment.
Cluster monitor privileges are needed to use this api in the follower cluster.
There was a problem hiding this comment.
Ditto, I'm not certain if it also needs cluster monitor privileges or only needs them.
|
|
||
| //==== Authorization | ||
|
|
||
| //TBD |
There was a problem hiding this comment.
This is the same as put and delete auto follow pattern APIs.
4 participants
Related to #35557
This PR adds authorization details for the remainder of the cross-cluster replication APIs.